This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/nextauthjs/next-auth/964cDCS73H27Y5dRF62r8hMmRMXu
✅ Preview: https://next-auth-git-fix-upgraded-require-optional-nextauthjs.vercel.app

🎉 This PR is included in version 4.0.0-next.4 🎉

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

@balazsorban44 Yeah strange, right? I couldn't find peerOptionalDependencies referenced anywhere online really. Not sure where that originated from haha.

Anyway, is your require-optional fork doing the trick?

peerOptionalDependencies comes from the require_optional package. It was written BEFORE peerDependenciesMeta was a thing. And no, unfortunately my solution did not work. Searching for peerDependenciesMeta up in the node_modules tree stopped looking for nodemailer in my next's package.json.. 😵 I start to think that the best option is to drop the database config, asking the user to explicitly choose a adapter, and use the form next-auth/providers/your-provider for importing built-in providers. (wrote about this here as well: #1682 (comment)). These two things would mean that we don't need any additional package for requiring optionally. Having imports like this would make it explicit and opt-in which packages you will have to use. I could use your help @ndom91 with testing.